3Com Corporation EtherDisk Diskette for the EtherLink III Adapters Troubleshooting If the adapter diagnostic tests fail, the adapter might not be defective. Check the following: 1. Make sure that the adapter is completely seated in its slot. Review the installation instructions in the appropriate adapter guide. 2. If you are running the Group 2 test, make sure that the adapter is securely connected to a loopback plug or to a properly cabled network. 3. If you are running the Group 3 test, make sure that the adapter is securely connected to a properly cabled network and an echo server is set up on the network. 4. If you are configuring the I/O base address, interrupt request level, or boot PROM base address, make sure that the settings you choose for these parameters do not conflict with any other peripheral or software program installed in the computer. For a list of system resources commonly used by other peripherals, select "Commonly used interrupt and I/O base addresses" from the "Configuration and Diagnostic" submenu. 5. Make sure that the configuration setting for the transceiver type is correct. 6. Running Group 2 tests while connected to an active network can cause intermittent failures. These failures can be avoided by using a loopback plug or by connecting to an inactive network on which only the computer being tested is operating. 7. If you installed a twisted-pair adapter, check the LED on the backplate of the adapter. The LED should be checked only during or after the diagnostic tests have been run. The LED will be on when there is a correct connection between the adapter and the hub. The LED will flash if the polarity of the connection is swapped. 8. The slot in the computer may be defective. Install the adapter in another slot and run the tests again. 9. The computer in which the adapter is installed might be defective. Install the adapter in a known functioning computer and run the tests again. 10. The loopback plug you are using might be defective. Try a different loopback plug. 11. Replace the failed adapter with a known working adapter, with the same configuration. If the second adapter fails, something is probably wrong with the test environment, not with the adapter. (%VER Troubleshooting v2.0d)